Minor fix to align Host and Core team references #599
Conversation
|
Thanks for this work! How did you do the translations? |
|
@rrrutledge As the changes are simple ones, I used different AI tools to get the translations. Those are also open to get a review or feedback for native speakers, if it is needed. |
|
I’m sorry I haven’t gotten to this. Still on my radar. |
|
Sorry it took so long to get to this. Our way of working has been to get a native speaker to review each machine-generated translation. This change is small, so it may not be needed, but let's try. |
|
I'll nominate the following people to review the given language translation. It will take you ~1min, so just do it now and leave your review? Thank you!
|
|
The translation sounds reasonable. Only caveat: it translates the term host team. If we do that in all German learning path segments and patterns that is fine, otherwise it may cause minor confusions. |
|
@rrrutledge thanks for the time estimate, that helped make the decision to squeeze the proof reading in just now |
Co-authored-by: rrrutledge <rrrutledge@users.noreply.github.com>
Co-authored-by: Arthur Fücher <arthurfucher@gmail.com>
Co-authored-by: Arthur Fücher <arthurfucher@gmail.com>
Co-authored-by: Arthur Fücher <arthurfucher@gmail.com>
|
Thank @afucher for your review and proposals! Changes accepted! |
| @@ -17,4 +17,6 @@ | |||
| 这个选项对调用团队很有效，因为他们在需要的时候获得了所需的功能，而无需承担解决方案的长期维护负担。这对于维护团队来说是有效的，因为他们能够更好地拓展和服务他们的消费者。它适用于整个公司，因为共享问题的解决方案最终都在共享的、集中维护的位置，任何人都可以使用它们。更多的工程时间集中于生成解决公司问题的代码，而不是花费在特性协商和问题升级过程中。 | |||
|
|
|||
| === 额外的资源 | |||
| * https://patterns.innersourcecommons.org/p/trusted-committer[Trusted Committer] 的模式。 | |||
|
|
|||
| * 主办团队通常以 https://patterns.innersourcecommons.org/p/core-team[核心团队] 模式表示。 | |||
There was a problem hiding this comment.
We use “主导团队” instead of “主办团队“ here, and we don't translate Trusted Committer , as it's hard to find a right Chinese term for it.
There was a problem hiding this comment.
Thanks @WillemJiang Could you double check that I committed the right changes?
| @@ -31,7 +31,7 @@ | |||
| * 主导团队的决策 | |||
|
|
|||
| 在可能的情况下，从团队对项目的内部定义到特定于项目的特殊情况场景，都应该清晰而详细地传达上述内容。 | |||
| 这种沟通应该以一种容易被非核心团队成员查询和理解的方式进行。 | |||
| 此沟通应以一种易于查询和理解的方式进行，以便那些不属于主办团队的人员能够理解。 | |||
There was a problem hiding this comment.
We use “主导团队” instead of “主办团队“ here.
There was a problem hiding this comment.
Thanks @WillemJiang Could you double check that I committed the right changes?
This PR is a small contribution to align some references between Host and Core team in the introduction learning path. This is part of the conversation of the issue #594 and it could help to resolve misunderstandings for the new readers.
A reference of the Core Team pattern is added in some places to facilitate the connection with it, and give a better context of this team in the InnerSource contribution workflow.
The PR includes also the traslation into the current languages the changes added here.